Skip to content

Adding docs for Unsafe Apis in System.Runtime.CompilerServices #2819

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Jul 25, 2019
Merged

Adding docs for Unsafe Apis in System.Runtime.CompilerServices #2819

merged 3 commits into from
Jul 25, 2019

Conversation

Anipik
Copy link
Contributor

@Anipik Anipik commented Jul 24, 2019

@carlossanlop carlossanlop requested review from mairaw and rpetrusha July 24, 2019 19:38
@carlossanlop carlossanlop added 🏁 Release: .NET Core 3.0 :checkered_flag: Release: .NET Core 3.0 new-content Indicates PRs that contain new articles waiting-on-reviews Indicates PRs that cannot be merged because of the lack of reviews labels Jul 24, 2019
@@ -1062,8 +1066,7 @@
<Docs>
<typeparam name="T">The type of reference.</typeparam>
<param name="source">The reference to subtract the offset from.</param>
<param name="bytesOffset">The offset to subtract.</param>
<param name="byteOffset">To be added.</param>
<param name="byteOffset">The offset to subtract.</param>
Copy link
Contributor

@carlossanlop carlossanlop Jul 24, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You removed one of the parameters from here. I suspect it was a duplicate. This happens when the parameter name does not match in the source file and the ref file. The official one is the one in the ref file. Which one is the correct one, can you please confirm?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yes byteOffset is the name of parameter in the ref file

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That is interesting because the Parameters section, signatures, etc. only shows one of them.

@joelmartinez is this a bug in mdoc?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I remembered there's another possible case: if the parameter name is changed from one version to another, they both show up, and both need to be documented, not just one.

@joelmartinez may know the true answer for this.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This issue should be resolved in the next mdoc release (5.7.4.10) ... ETA is soon, but not immediately, so manual interventions for this is ideal.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I thought of this too but then the parameter would have additional information to convey this like here where you see different frameworkalternate values for each parameter:
https://github.com/dotnet/dotnet-api-docs/blob/master/xml/Microsoft.VisualBasic/Collection.xml#L1161

Copy link
Contributor

@carlossanlop carlossanlop left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for submitting this change. I left a few comments. Can you please take a look? Let's also wait for Maira/Ron to jump in.

Copy link
Contributor

@mairaw mairaw left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A few comments but looks good overall @Anipik!

@@ -1062,8 +1066,7 @@
<Docs>
<typeparam name="T">The type of reference.</typeparam>
<param name="source">The reference to subtract the offset from.</param>
<param name="bytesOffset">The offset to subtract.</param>
<param name="byteOffset">To be added.</param>
<param name="byteOffset">The offset to subtract.</param>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That is interesting because the Parameters section, signatures, etc. only shows one of them.

@joelmartinez is this a bug in mdoc?

@mairaw mairaw added this to the July 2019 milestone Jul 24, 2019
Co-Authored-By: Maira Wenzel <[email protected]>
Copy link
Contributor

@carlossanlop carlossanlop left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it looks good now, @Anipik. Thanks for making the change.
@mairaw if it looks good to you, we can get this merged.
Pending (but not blocking) @joelmartinez 's help to determine why there was a parameter vs param name mismatch.

@mairaw mairaw merged commit 503d60d into dotnet:master Jul 25, 2019
@mairaw mairaw removed the waiting-on-reviews Indicates PRs that cannot be merged because of the lack of reviews label Jul 25, 2019
@Anipik Anipik deleted the unsafe branch July 25, 2019 20:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🏁 Release: .NET Core 3.0 :checkered_flag: Release: .NET Core 3.0 new-content Indicates PRs that contain new articles
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants